home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
HPAVC
/
HPAVC CD-ROM.iso
/
$GSPPX11.ZIP
/
PPLX.DOC
< prev
next >
Wrap
Text File
|
1995-06-02
|
12KB
|
302 lines
▄▄▄▄▄▄ ▄
▄█▀▀██████▄ ▄
█ ██████▀ ▄▄█████████████▀ ▄▄▄▄▄▄▄▄▄▄ ▀▄█ ▄ ▄▄▄▄▄▄▄▄▄
░▀ ▐██▀██ ▄██▀▀▀ ▀█▀ ▄▄█████████████▄ ████▄ ▄███████████▄
░ ██▌ ▐█ ██ ░ ██▀▀ ▄▄▄▄▄▄▄▄▄ ▀█ █ ▄ ▄ █▀ ▄ █
██ █ ▀█ ██▀ █▀ ▀▄▄ ▄▄██▀ █▄ ▀▌ ▄
▐█▌ ▐█ █ ▄▄▄▄█▄▄▄▄▄ ██ █ ▀▄ ▀██ ▀████████▄
██ █ █▄ ▀░ ▀█ ██▄ █ ▄▀▀▄ █ ███ ░▀▀▀▀▀▀▀▀▓▓▄
██ ▄ █ ▀█▄ ░ ██ ▀▄ ░ ▀▄ █ ███ ▀██
▐█ ▄███▄ █ ▀█▄ ██▄ ▀▄▄▄▄▄ ▄▄▀ ██ ███ ▄ ▄██
▄▄ █▄ ░ ▄██ ▀██▄▄ ▄ ▄▄█▄ ▀██▄▄▄▄▄ ▀▀ ▄▄███ ██ ▄█ ▀ ▄▄▓▓█ ▀
█ ▀ ▄██ ░▀▀█▄ ▀▀██████████▄ ██████████████ ▄██ ███████████▀ ░
▌▀▄▄▄██▀▀ ░ kP<aRT>░▀███▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄ ▄ ▄ ▄ ▄
▌
▀ ▀ ▀ ▄ ▄▀ ▀▄█ █▀▀ █▀▒ █▀▒ █▀▒
▄ ▀ ▀ ▄ ▀ ▄▀▄ █ ▓▄▄ ▓▄█ ▓▀▄ ▓▀▀
· · ·-─────────────────--· · ·
P.P.L.X - 1.O1
· · ·-─────────────────--· · ·
PCBoard Programming Langage eXtractor
(C) 1995 Lone Runner
Main Coding - Lone Runner
Parts - The doC
─────────────────────--· · ·
■ READ BEFORE USING !
─────────────────────--· · ·
You may use this program provided that :
- You are not part of any federal group (i don't like federal groups ;))
- You are not part of Clark Development Company (nothing personnal...)
- You planed to use it at home for personnal purposes only (no money here!)
THE AUTHOR MAY NOT BE RESPONSIBLE FOR ANY CHANGE MADE TO ANY PROGRAM
BY USING PPLX. Nobody will ever ever enter an action against Borland
because they made Turbo Debugger or to V Communication because they
made Sourcer. There is no more reason for PPLX author to be responsible
for any law violation by using this software.
If you don't agree with the above terms or if you are not in accordance
with restriction use, you HAVE to delete this software IMMEDIATLY.
Further use of this software will be consider as the acceptance of the
above terms.
─────────────--· · ·
■ DESCRIPTION
─────────────--· · ·
PPLX is a PPE decompiler... working with PPE's up to 3.10 and, handling
FUNCTIONS & PROCEDURES. (yes!! ;))
1.O1 follows 1.OO and corrects a small bug that prevent PPLX from
decompiling some PPE's in very special circumstances (actually, i only
saw this happen one time ;))
v1.OO followed v1.OOß1 and corrected a number of bugs/mistakes/changes...
Previous version (beta) was decompiling about 80% of PPE's 2.O & 3.x
(and almost NO PPE v1.O ;)) This version decompile 100% of my PPE collection
(227 files). Some does not recompile due to unused functions, but they only
need 2/3 changes to be recompilable. I don't think that 100% of the PPE's
you will try to decompile will work, but i tested enough to evaluate the
percentage of success to more that 99%.
──────────────--· · ·
■ INSTALLATION
──────────────--· · ·
Hmm... copy it to your UTILS\ or WHATEVERITISCALLED\ subdirectory,
preferably in your PATH...
────────────--· · ·
■ USING PPLX
────────────--· · ·
Type PPLX FILENAME[.PPE] [/DEBUG]
/DEBUG was only intended for debugging purposes... Using this switch
will give you some iinformations on the current decompiling process,
completly UNusefull unless you found a PPE that does not decompile and
you want to mail me some informations...
WARNINGS/ERRORS
"Function is declared but not defined, code may not recompile..."
This means that, in the original source code, a function was coded but not
used. When PPLC compile the source, if a function is not used, it doesn't
update a important field that holds the function coordinates... In this
case, PPLX will not be able to detect the beginning of the function, and,
if there are local variables, to declare them. The same problem may appear
with procedures.
"Unknown statement xxxx, dunno how to handle it... Skipping!"
This means that an unknown stateemnt was used, theorically, this cannot
happen, but in real life, a corrupted PPE or a anti-decompilation trick
can produce this warning. If an unknown stateemnt is found, it is skipped,
causing some next statements to be irrationnal... Code may redecompile
correctly after some instructions but it is not likely that the code will
be recompilable.
"Unknown function xxxx, dunno how to handle it... Aborting!"
This is a fatal error, an unknown function cannot be skipped, it is due
to the same things (corrupted PPE, anti-decompialtion trick) but cannot
recover.
"FATAL ERROR! ..."
Any error message beginning by "FATAL ERROR" means that the PPE cannot be
decompiled due to different reasons... following message may not be clear
for you but if you write me a mail about the error, tell the PPE name,
and the error message.
FOR/NEXT/WHILE/IF/THEN/CASE/...
Don't be surprised by a strange line of code, for example "If (1 < 0)" is
often used to initiate a FOR/NEXT loop... This is due to PPLC that convert
all loops to IF/GOTO... That's lame, yes, but that's the way it is... :(
BACKDOORS
Don't be shy ;) Decompile all your PPE's, and check the statements/functions
usage report, a GetAltUser in a JOIN replacement may be strange ;)
PPE'S RUNNING DIFFERENT AFTER BEEING DECOMPILED & RECOMPILED
Some PPE's (CSSC for example) compute a self check to see if they were
decompiled and recompiled... It is not a big deal because you have the
source so you can remove the self-check test.
───────────────────────--· · ·
■ WARNINGz / DISCLAIMER
───────────────────────--· · ·
■ This decompiler should work perfectly on your machine as it is the
case on mine. However, some PPE may not decompile, due to some new
anti-decompilation tricks that maybe will cause PPLX to crash... It is
possible, also, that PPLX crash or fail to decompile a PPE because of a
special instruction chain that i didn't manage to handle... In such a
case, please mail me a description of the error and the name of the PPE
that failed to decompile...
■ Do what you want with this... You may use this program in any way you
want, you may destroy it, burn it, eat it, smoke it, inject it, vomit it,
kick it, suck it, piss it, shot it, print it with reversed lines, rename
it to zip, arj, arc or whatever you want, try then to extract it, to
pkzipfix it, you may also perform sort on it, uuencode, crypt it with
PGP, play it on your GUS or even your SB, you may even decompile, modify
it, you may do WHAT YOU WANT, but NO MEMBER OF AEGiS CoRP MAY BE
RESPONSIBLE FOR ANY DAMAGE CAUSED BY THE USE OF THIS PROGRAM OR IT'S
MODIFICATIONS...
─────────────--· · ·
■ FINAL WORDS
─────────────--· · ·
■ Chicken/ECR
Hi man ! Thanks to you for your eXXXcellent PPLD, even if we are still
waiting for the function/procedures support ;) Anyway, this was an gr8
program... We hope that you will like this one and that you will take
this maybe as a competition for the best decompiling code ;) Well, if
you want to discuss about PPE (de)compilation/(de)crypting, feel free
to contact me at the adress bellow, i would love this!
■ Clark Development Company
C'mon men, smile... decompiling a PPE was not a so big deal... it took
me 'bout 1 hour to make a decrypting system... the decompilation engine
took about 1 week to be operationnal... I remember something said in
a well known magazine : "PPE 3.x are more secure than EXE files...I doubt
that we will see one day a decompilation program for the new PPE format"
Well, see, there are now two of those decompilation programs out there...
Stop crypting, stop adding new tricks into the decompilation procedure,
stop changing small details that crash our decompilers... Remember that,
even if we (Chicken and me) are stopped by a new trick, there will always
be someone to defeat you... simply because your PPE need to be decrypted
by PCB itself... so you have no other choice that let a way to decrypt
them...
You want a suggestion ? Make a real compiler that generate OBJ code...
■ Shareware PPE Coders
Well, sorry men, I also make PPE's, and very large ones that take many
months of programming, but asking money for such pieces of crap is lame...
■ PCB Sysops
Well, you wanted a decompiler that works with functions & procedures...
now you have it ! Just hope it works on the special PPE you wanted
to decompile since 8 months ;)
I don't care that you will decompile and modify code, simply note that
decompiling and changing a program may be good (debugging, customization,
removing delays ;) , ... ) but, never, i said NEVER, change a copyright
notice... We have seen too many sysops changing PPE's authors name and
doing such lame operations... respect the work of a good coder... don't
be lame, let his name and notices...
■ Lamers
Ok, with this you will put backdoors and make new releases of PPE's...
I don't care... simply because if you can put a backdoor, we can also
decompile all PPE's that are about to be installed on our systems and
have a total control over the code... so don't bother, go to hell
immediatly, don't wait to die... thanks.
■ Everybody
Suggestions ? Contacts ? (legal only)
Write to : lone.runner#dln@sparkhq.fdn.org
────────--· · ·
■ GREETS
────────--· · ·
The doC/AEGiS - Thanks for your support in brainstormings
while trying to guess how was coded this
stupid PPE format ;)
Gandalf/Infiny-AEGiS - Still on this F*cking Windows proggy he? ;)
Number Six/AEGiS - So, i managed to decompile 100% of your
PPE's ;) do you have some more ? :)
New ID/Massive Posse - Ragga rulez!
Jason Bourne/AEGiS - Legalize !!!
Ferem Destroy/MWB - Did you finish you realtime-gouraud-shaded-
fractal-landscape-with-integrated-phong-
and-mutating-multitasking-code-impossible-
to-trace ? :))
Kloy / (┤RT - Thanks for those kewl ASCIIz!
HACKTiON - your are kewl guyz, make more prods!
PWA - Is the PPE section still alive ? Hope so...
anyway, thanks to you guys, to have made
the world of PPE's so competitive...
All (good ;)) PPE Groups - Go on, continue to release new products,
and feel free to chat with AEGiS members,
write to aegis.corp#dln@sparkhq.fdn.org !
_.LoNE RuNNeR
_ _ _ ___ ___/\
_________/\ /\_____________/\________________ ___ _ _ \/\______________
/ _ \/ _________ / ______________________ / __________ /
_/ __/ \ ____)___\/ \ \_/ \/\___________ \/_
\ \ \_ \ \_ \__ \_ \_ / /
\______\ /____________/________________/_____________/____________/kP
·-------`------'---------------------------------------------------------·